We have Windows Std Server 2003 and Exchange Server 2003 and all the users are using Outlook 2000. Now we have some users with Outlook 2007 and it works fine from office but when users trying to connect from home using VPN, Outlook 2007 opens(outlook 2000 wrks fine from home for same user)but it does not connect to my exchange server. I believe it is a problem of SSL as I get error autodiscover.domain.com (the name on the security certificate is invalid or does not match the name of the site). Last year I installed Standard SSL from GoDaddy for IPHONE setup but our IPHONE did now work so I unistalled (cancelled) SSL. Can you please guide me how do I solve this problem. Is there any settings where I need to look. (I have desktop at home where I have installed Office 2007 before I installed SSL and that works fine but recently new laptop we buy with Outlook 2007 does not work from home. OWA works fine. Thanks,

Try this link for some suggestionshttp://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/e05d29c8-48b0-4ff5-8f57-3df809b7bad9/ Andrew Sword, MVP

Thanks Endrew for your help.I went through the post but it did not help me for my issue.

Hi, Please attempt the following method to check the issue: 1. Configure the Outlook 2007 to use Password Authentication (NTLM) instead of default Negotiate Authentication (More Settings | Security | Logon Network Security). Then, check the whether the issue persists. 2. If the issue still persists, would you please let me know the issues symptom more detailed. For example, whether any error is encountered when attempting to connect to Exchange Server such as Exchange Server is not available? Or you are prompt for enter the password again and again. Whether you have encountered any problems when checking name when configuring Outlook profile? Note: Regarding the certificate error, I would like to explain that the autodiscover is a new feature of Exchange 2007 and Outlook 2007. If you have Exchange 2003, you should not receive the error unless the client is able to resolve the autodiscover.domain.com to a web site. In any case, the certificate error should not affect the Outlook to connect to Exchange Server. Therefore, I think that we can temporarily ignore the certificate error. 3. Please check the Application log on the Exchange Server. Whether any 9646 event can be located? If yes, please refer to following articles to check whether the issue can be solved. http://msexchangeteam.com/archive/2007/07/18/446400.aspx http://support.microsoft.com/kb/842022/en-us Mike

Thanks Mike for your response. Greatly appreciated.I have already configured outlook 2007 to use Password Authentication (NTLM). I get following errors; When I open outlook after authentcating VPN, Outlook 2007 opens and trying to connect to Exchange Server and after a minutes or so it says "Disconnected" (this message shows bottom right corener of OUtlook) As I said earlier it works from Office without any problem. However in office, when I try to use Repair option it tells me that Serverisnot avaliable(I don't have exact message rightnow as I don't have laptop with me) So I don't understand why it does

any update on this issue.I changed FQDN in host file (instead of 192.168.1.6servername to 192.168.1.6 servername.domain.domain.com)Still it does not work.

Have you tried using Outlook in RPC Diag mode? Start-->Run-->Outlook /rpcdiag

Thanks Vanir I alreadys have used this command to check.However I called Dell Tech Support to help me and I changed following and worked.I made changes in Account Settings > General Tab > Changed from Automatically Detect connection state to Manually Control connection state. After making this changes it worked .

Hi Mike, I have a remote user facing this issue. I have tried all settings suggested, still the same. The main symptom is the user is prompted for login and password again and again. This is a new remote setup that worked for 3-4 days, then this issue started. Tried a repair on Outlook, and I have other VPN users who can connect. This one is the only Windows 7 user, but it was working originally. Hope this info is what you need to help troubleshoot this.